Defining and creating requirements for an application is an iterative process that requires input from all stakeholders. If the information about a requirement is detailed and up-to-date, the requirement is more useful during the application development process.
Some requirements are non-functional and others articulate specific business rules that the application must satisfy. While you can specify requirements in the specification description, if requirements are shared by multiple specifications, a best practice is to separate the requirements into individual ones and associate them with the related specifications. You can reference requirements in application rules, specification rules, and flows.
From the Application Overview landing page, access requirements by clicking the Requirements link in the Details section.
This tab lists any requirements that are currently defined for the application. You can filter the list of requirements based on importance and status. You can also filter by searching for keywords in the requirement name and description.
Note: After you create a requirement, you cannot modify its name, ruleset name, and ruleset version. The requirement name and ruleset name are displayed as links that you can click to open in the work area of Designer Studio. The ruleset version is displayed as part of the ruleset name link.